Release 10.1A: OpenEdge Deployment:
WebClient Applications

Setting up the application on the AppServer machine

The following section provides information about applications on AppServer machines.

To set up the application on the AppServer machine:
  1. Verify that an OpenEdge development product was installed on the AppServer machine and the person doing the installation, when presented with the Setup Type window, chose the complete installation, as opposed to the typical installation or the custom installation.

  2. Recursively copy the back-end files of the Sports2000 application from the %DOCS%\src\sports2000\gui directory to the AppServer work directory.

    3. Note: The gui directory contains both back-end and front-end application files.

  3. Create a copy of the sports2000 database on the AppServer machine. The copy can reside anywhere, but note its full path. For example, d:\wrk91b\sports2000.db.

  4. Start a database server for the sports2000 database running on the AppServer machine. Use Progress Explorer or a proserve command similar to the following:

    5. %DLC%\bin\proserve d:\wrk91b\sports2000.db

  5. Compile the sports2000 back-end application files you copied to the AppServer working directory in Step 2, as follows:

    1. Start an OpenEdge session.
    2. Connect to the sports2000 database.
    3. Use the PRO*Tools PROPATH tool to add the AppServer working directory to the PROPATH.
    4. Start the Application Compiler, select Options Compiler, (optionally) set Minimize R-code Size to Yes, and click OK.
    5. In the Application Compiler’s main window, click Modify, enter the path of the AppServer working directory, click OK, and compile the application.
  6. Use Progress Explorer to configure the default asbroker1 AppServer instance, as follows:

    1. In the General Options for Broker tab:

      2. Change the broker working directory to the AppServer work directory.

      In the Appservice Name list, add the service name sports2000partition.

    2. In the General Options for Server tab:

      3. Add the database connection parameter to Server Startup Parameters. For example, if the Sports2000 database resides at d:\wrk91b, add the following parameter: 

      -db d:\wrk91b\sports2000

  7. Use Progress Explorer to configure and start the controlling NameServer instance for the asbroker1 AppServer.

  8. Use Progress Explorer or the asbman command to start the asbroker1 AppServer instance. For example (using the asbman command):

    9. %DLC%\bin\asbman -name asbroker1 -start

Copyright © 2005 Progress Software Corporation
 www.progress.com
Voice: (781) 280-4000
Fax: (781) 280-4095